We're talking about the same thing. Yes, I'd have to
generate the speed myself, from two different stills.
My problem was, how I could do that, if all that I've
got is one Macro, which returns me the different
stills, and all I can actually get from there is a boundary
box: Having several stills of boxes which may or may
not be the same size, not to mention will never rotate,
won't give me the possibility to calculate the speed.

I'm not a total newbie, there is some stuff I do know. :-)

Anyways, you and I were saying exactly the same thing,
just that you have been commenting from the side of
"you need to handle and generate speed yourself, you
can't retrieve it somehow from POV" and I was asking
just that. To me, it seems like we're trying to argue the
same point.

But I think we're behaving well, aren't we? :-)

--
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde

>
> > So, if I can check object at X=0 and at X=.1, I've possibly
> > got two different positions for the object, but there might
> > as well be two different objects, if the macro switches
> > between objects according to the X-Value.
>
> It *is* two different objects. An object only has current state, no
> information about past or future state. X is just a parameter for
> generating the object. The clock value only has any meaning to the code
> that generates the objects for the current frame. For each frame, it is
> just a number.
> Did you think an object with a transform based on clock was actually
> moving? It's not, it is just a series of stills. There is no motion
> information to retrieve, you have to handle it yourself.
>
> --
> Christopher James Huff <cja### [at] earthlinknet>
> http://home.earthlink.net/~cjameshuff/
> POV-Ray TAG: chr### [at] tagpovrayorg
> http://tag.povray.org/

Post a reply to this message